#software troubleshooting

[felixcloud6288]

I kept hitting some weird issue where OBS recognized my capture card but it couldn't play video from it (Audio worked fine). If I unplugged my card and plugged it back in, video would work and audio wouldn't.

Only thing I could do to fix it was restart my computer.

Figured out what was going on. It was Discord. When Discord is open, it detects OBS and starts using the same video channel as OBS. Then when OBS is closed, Discord stays connected to it and then OBS can't reconnect because the channel is busy.

Solution was to completely close Discord before starting OBS.

[pumpkinsplicelatte]

I don't know who needs to hear this but:

Restart your computer.

Obviously this doesn't apply to everyone but if you're having computer trouble restart it. It solves like 90% of computer problems because the computer will forget what the problem was and go back to being normal.

[laptopcare]

Get professional laptop onsite support service at your doorstep. Our expert technicians provide fast and reliable repairs, software troubleshooting, and hardware upgrades at your convenience. Book our laptop onsite doorstep support service for hassle-free assistance today!

Visit :- https://www.laptopcare.co/doorstep-service/

[apple-cores]

but is it edible

preview of something im gonna casually help with. moused bcs i was troubleshooting my tablet (zoomed out)

[frog707]

Technical writing part 2

My plan to devote April to writing a tutorial (for my Jolt-JNI open-source software library) went about as I expected. 7 days into May, the tutorial still isn't in a presentable state. Hard to predict when it will be ready, but I'm glad to report I've launched the website and established some forward momentum. I've also built some confidence, both in the library and myself. So progress.

A week spent visiting family in another state didn't help. I made almost no progress on software during that time. Not because I was busy or jet-lagged. More like the environment wasn't comfortable for long stretches of keyboard work.

I've heard you don't really understand something until you can explain it to others. Even as I write tutorial pages for Jolt JNI, I'm learning how to use to library. I typically start writing about a feature with only a vague notion of how it should work, based on similar projects I've used in the past. Then I write a short sample app to demonstrate the feature. Often the sample app doesn't work as expected. I find myself troubleshooting the library, the app, and my own expectations, all at the same!

It feels risky to be teaching things I don't fully understand myself. If I'm mistaken about how/whether something works, I might badly mislead people. Such thoughts trigger (irrational) fears of being exposed as an imposter.

But I'm not an imposter. In fact, I might even be the ideal person for this task. Not only did I write the damned library, but I have a plethora of experience with similar libraries. I'm skilled at troubleshooting unexpected behavior. I've written similar tutorials before. And of course I'm fluent in English. It's still difficult.

In a way, my ignorance is a good thing, because I'm still at or near the level of experience of my target audience.

Expertise is valuable, but it gets in the way of writing for beginners. Beginners require explanations of things that seem obvious to experts. Once one becomes an expert, it gets hard to remember how beginners think.

[highretrogamelord]

B.A.T. for DOS

[deanpinterester]

well of COURSE my microcontrollor had to die on me Right when i wanted to test it with the rest of the project even though it was working perfectly the day before 🤡

here's a preview if anyone's interested

[wollemi-whump]

any gifmakers know any good/high quality screen recording programs for mac?

[springcatalyst]

i have a disease that makes me start new projects i have 0 of the skills for and yeah. it's incurable

[pyjamaenzel]

me: (details the steps i did to troubleshoot the printer, which INCLUDED power cycling it when nothing else worked)

it guy: the error message you are getting [after you turned it back on] means that the computer is off. Try turning it off and on again.

me: for the love of god i know you have to work with idiots all the time but i was trying to make your job easier. I would not have put in a ticket if that WORKED

[blacksails2017]

Me when the .01% chance of happening thing that is stress dream material happens to me on my 3rd time ever doing the thing

[thenarrativefoil]

[cai-tan]

Hey, Tumblr, I'm angry and frustrated and I'm making it your problem.

Break the Keep Reading only if you either A. have any experience with OBS-Websocket or other such integrations, or B. sincerely wish to partake in my suffering. Warning for excessive cursing, it gets rough.

Update on the whole KT-1632 overlay situation: After a handful of minor technical difficulties and rookie mistakes (hey cat, it would help if you actually turned on the damn websocket before trying to connect to it), I've established a base framework for connecting to OBS Websocket.

Once I had that in place, I started testing out what kind of messages I can get, and uh... I'm already running into a huge problem, here.

See, OBS Websocket 5.0 has the following messages that seem pertinent to my use case: CurrentProgramSceneChanged, SceneTransitionStarted, SceneTransitionEnded, and SceneTransitionVideoEnded. Keep in mind, the only documentation I can access right now, as far as I can tell, is just the 5.0.1 OBS-Websocket.

Here's a refresher on the use case: I want to be able to move elements of my Unity-based stream overlay depending on which scene is currently active in OBS. A wrinkle in this is that I use a custom stinger transition with a specific cut point, like this:

Now, all three events regarding the scene transition only have one piece of data to them: the name of the transition (which is basically always going to be "SniperScope"). The only event that actually tells me what scene is being switched to is the CurrentProgramSceneChanged event.

There is an immediate problem.

Funnily enough, this order of operations is actually backwards from the current documentation:

On the one hand, there could potentially be some sort of delay or other issue involved with WebsocketSharp / Unity that's responsible for this, however in my testing the exact amount of delay and order of operations is entirely consistent every single time I initiate a transition in OBS. The first message almost always arrives instantaneously; it's the other three messages that seem to come whenever they feel like it, and not at all close to what they need to be at.

On the other hand-- wait, what? What's this issue on the official obs-websocket github about--

So you're telling me that SceneTransitionStarted used to have the from and to scenes specified in the event data in version 4, and they removed it in version 5 for literally no other reason than an RPC overhaul? And they haven't added it back in OVER A YEAR?!

Now, the github actually does have an install link for obs-websocket version 4.9.1-compat that should (keyword should, you know how that goes) work with OBS 29 (more specifically, it should work with 28+, which means there isn't even a guarantee for it to work with OBS 29... fucking awesome).

However, uhhhhhh... I cannot find ANY FUCKING DOCUMENTATION FOR 4.9'S PROTOCOL WHATSO-FUCKING-EVER. There is LITERALLY ONLY 5.0 in the readmes and protocol.md docs.

This shit has me pulling my hair. I'm goin' the fuck to sleep. Anyone got any bright fuckin ideas, I'm all fuckin' ears for it in the morning.

[snepril]

I vividly recall an incident when I worked at a tech job. I was our most experienced programmer on my team, and we were discussing issues with a lil software widget that was very technical. Suddenly, one of my coworkers - the one that I was actively training - started butting in, interrupting me and cutting me off so they could answer instead. At first I wrote it off to latency, but it just kept happening. And weirder still, my boss - who knew all of this - was listening to his demonstrably wrong input over mine!

It took me a few minutes to realize what was going on: my coworker was a guy. I am not. And though it was my first experience with mansplaining, it was not my last.

A rite of passage for all trans women.

This should go without saying as well but, womens issues is not fully encapsulated in this comic. Its a light hearted way to talk about it, but it is infinitely more nuanced, systemic, and difficult to discuss than a 10 panel mini comic will allow.

Women are more than these problems, and these problems are not all that women face.

Also i see all these wonderful asks your all so sweet, ill be getting to them soon.

[digimobphonerepairs]

Quick & Professional Laptop Repair Service Near You

Digimob Phone Repair offers comprehensive laptop repair service tailored to your needs. From virus removal to hardware upgrades, our expert team ensures your laptop runs smoothly, combining fast service with affordable pricing and trusted expertise.